Dynomotion

Group: DynoMotion Message: 8464 From: Hugh Sontag Date: 10/11/2013
Subject: EStop thread terminated by KMotionCNC?
Hi Tom,

I have a thread running continuously on KFLOP, checking for an estop switch, and if the switch opens, all axes are disabled.

But it appears when I move the axes using KMotionCNC, the estop thread is terminated.

How can I ensure that that thread runs all the time, even when KMotionCNC is being used?

Thanks,
Hugh
Group: DynoMotion Message: 8465 From: TK Date: 10/11/2013
Subject: Re: EStop thread terminated by KMotionCNC?
Hi Hugh,

Only one program can run in a Thread at a time. If you launch another program to run in the same thread at the same it will terminate the previous. I suspect you might have an MCode or something using the same thread. 

The Stop Button also stops all threads from executing except Thread 1

Regards
TK

On Oct 11, 2013, at 12:55 PM, Hugh Sontag <hsontag@...> wrote:

 

Hi Tom,

I have a thread running continuously on KFLOP, checking for an estop switch, and if the switch opens, all axes are disabled.

But it appears when I move the axes using KMotionCNC, the estop thread is terminated.

How can I ensure that that thread runs all the time, even when KMotionCNC is being used?

Thanks,
Hugh
Group: DynoMotion Message: 8466 From: Hugh Sontag Date: 10/11/2013
Subject: Re: EStop thread terminated by KMotionCNC?
Hi Tom,

I'm using KMotionCNC with default settings, except for the X, Y, and Z axis encoder counts per inch. I checked all MCodes and User Buttons in the Tool Setup, and they are all "None".

I happen to be using Thread 6 for my estop thread.

Does KMotionCNC use one or more threads to do things like jogging the axes for the user interface? Maybe it uses Thread 6?

Thanks,
Hugh



On Fri, Oct 11, 2013 at 4:45 PM, TK <tk@...> wrote:
 

Hi Hugh,

Only one program can run in a Thread at a time. If you launch another program to run in the same thread at the same it will terminate the previous. I suspect you might have an MCode or something using the same thread. 

The Stop Button also stops all threads from executing except Thread 1

Regards
TK

On Oct 11, 2013, at 12:55 PM, Hugh Sontag <hsontag@...> wrote:

 

Hi Tom,

I have a thread running continuously on KFLOP, checking for an estop switch, and if the switch opens, all axes are disabled.

But it appears when I move the axes using KMotionCNC, the estop thread is terminated.

How can I ensure that that thread runs all the time, even when KMotionCNC is being used?

Thanks,
Hugh
Group: DynoMotion Message: 8467 From: TK Date: 10/11/2013
Subject: Re: EStop thread terminated by KMotionCNC?
Hi Hugh,

No Threads are used to Jog.

Don't you at least have an Init or Home button configured in KMotionCNC?

The Stop button would kill Thread 6. 

Normally you would add your EStop Loop to the end of your Init Program and assign a User Button to run it in Thread 1.

Regards

TK 

On Oct 11, 2013, at 3:14 PM, Hugh Sontag <hsontag@...> wrote:

 

Hi Tom,

I'm using KMotionCNC with default settings, except for the X, Y, and Z axis encoder counts per inch. I checked all MCodes and User Buttons in the Tool Setup, and they are all "None".

I happen to be using Thread 6 for my estop thread.

Does KMotionCNC use one or more threads to do things like jogging the axes for the user interface? Maybe it uses Thread 6?

Thanks,
Hugh



On Fri, Oct 11, 2013 at 4:45 PM, TK <tk@...> wrote:
 

Hi Hugh,

Only one program can run in a Thread at a time. If you launch another program to run in the same thread at the same it will terminate the previous. I suspect you might have an MCode or something using the same thread. 

The Stop Button also stops all threads from executing except Thread 1

Regards
TK

On Oct 11, 2013, at 12:55 PM, Hugh Sontag <hsontag@...> wrote:

 

Hi Tom,

I have a thread running continuously on KFLOP, checking for an estop switch, and if the switch opens, all axes are disabled.

But it appears when I move the axes using KMotionCNC, the estop thread is terminated.

How can I ensure that that thread runs all the time, even when KMotionCNC is being used?

Thanks,
Hugh
Group: DynoMotion Message: 8468 From: Hugh Sontag Date: 10/12/2013
Subject: Re: EStop thread terminated by KMotionCNC?
Hi Tom,

Thanks for the information.

I haven't created an Init Program per se yet. I have programs that initialize each of the axes, and I have (to date) run them from KMotion, not KMotionCNC.

The Stop button may have been how my estop thread was terminated. I'll put the estop functionality in Thread 1.

Hugh


On Fri, Oct 11, 2013 at 6:39 PM, TK <tk@...> wrote:
 

Hi Hugh,

No Threads are used to Jog.

Don't you at least have an Init or Home button configured in KMotionCNC?

The Stop button would kill Thread 6. 

Normally you would add your EStop Loop to the end of your Init Program and assign a User Button to run it in Thread 1.

Regards

TK 

On Oct 11, 2013, at 3:14 PM, Hugh Sontag <hsontag@...> wrote:

 

Hi Tom,

I'm using KMotionCNC with default settings, except for the X, Y, and Z axis encoder counts per inch. I checked all MCodes and User Buttons in the Tool Setup, and they are all "None".

I happen to be using Thread 6 for my estop thread.

Does KMotionCNC use one or more threads to do things like jogging the axes for the user interface? Maybe it uses Thread 6?

Thanks,
Hugh



On Fri, Oct 11, 2013 at 4:45 PM, TK <tk@...> wrote:
 

Hi Hugh,

Only one program can run in a Thread at a time. If you launch another program to run in the same thread at the same it will terminate the previous. I suspect you might have an MCode or something using the same thread. 

The Stop Button also stops all threads from executing except Thread 1

Regards
TK

On Oct 11, 2013, at 12:55 PM, Hugh Sontag <hsontag@...> wrote:

 

Hi Tom,

I have a thread running continuously on KFLOP, checking for an estop switch, and if the switch opens, all axes are disabled.

But it appears when I move the axes using KMotionCNC, the estop thread is terminated.

How can I ensure that that thread runs all the time, even when KMotionCNC is being used?

Thanks,
Hugh